Location based sharing of a network access credential

ABSTRACT

A network access credential can be shared among devices based on location information for a device. Location information can include timed fingerprint location information. In an aspect, location information can be associated with a location of user equipment. This location information can be correlated with network access credentials. Location information can be used to access a relevant network access credential. The relevant network access credential can be shared with other devices. In an embodiment, sharing a network access credential can be between mobile devices. In another embodiment, sharing a network access credential can be between a remote computing device and a mobile device. Sharing a credential can allow for access to a network without having to generate or input new credentials.

RELATED APPLICATIONS

This application is a continuation of, and claims priority to each of,U.S. patent application Ser. No. 16/434,164, filed on 6 Jun. 2019, andentitled “LOCATION BASED SHARING OF A NETWORK ACCESS CREDENTIAL,” whichis a continuation of U.S. patent application Ser. No. 16/108,060, filedon 21 Aug. 2018, now issued as U.S. Pat. No. 10,362,066, and entitled“LOCATION BASED SHARING OF A NETWORK ACCESS CREDENTIAL,” which is acontinuation of U.S. patent application Ser. No. 15/603,416, filed on 23May 2017, now issued as U.S. Pat. No. 10,084,824, and entitled “LOCATIONBASED SHARING OF A NETWORK ACCESS CREDENTIAL,” which is a continuationof U.S. patent application Ser. No. 14/957,525, filed on 2 Dec. 2015,now issued as U.S. Pat. No. 9,667,660, and entitled “LOCATION BASEDSHARING OF A NETWORK ACCESS CREDENTIAL,” which is a continuation of U.S.patent application Ser. No. 14/530,605, filed on 31 Oct. 2014, nowissued as U.S. Pat. No. 9,232,399, and entitled “LOCATION BASED SHARINGOF A NETWORK ACCESS CREDENTIAL,” which is a continuation of U.S. patentapplication Ser. No. 13/291,917, filed on 8 Nov. 2011, now issued asU.S. Pat. No. 8,909,247, and entitled “LOCATION BASED SHARING OF ANETWORK ACCESS CREDENTIAL.” The entireties of the aforementionedapplications are hereby incorporated by reference herein.

TECHNICAL FIELD

The disclosed subject matter relates to network access credentials and,more particularly, to sharing network access credentials.

BACKGROUND

Conventional sources of location information for mobile devices arebased on a wide variety of location determination technologies, such asglobal positioning system (GPS) technology, triangulation,multilateration, etc. These sources of data have provided theopportunity to capture location information for a device and share itwith another device, which can allow non-location enabled devices toparticipate, at some level, in location-centric services. In contrast toconventional systems that rely on technologies such as GPS,triangulation, multilateration, etc., the use of timed fingerprintlocation (TFL) technology can provide advantages over the conventionaltechnologies. For example, GPS is well known to be energy intensive andto suffer from signal confusion in areas with interference between thesatellite constellation and the GPS enabled device. Further, GPS issimply not available on many mobile devices, especially where thedevices are cost sensitive. Multilateration and triangulationtechnologies are computationally intensive, which can result inprocessing time issues and a corresponding level of energy consumption.

The above-described deficiencies of conventional mobile device locationdata sources for transportation analytics is merely intended to providean overview of some of problems of current technology, and are notintended to be exhaustive. Other problems with the state of the art, andcorresponding benefits of some of the various non-limiting embodimentsdescribed herein, may become further apparent upon review of thefollowing detailed description.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is an illustration of a system that facilitates sharing a networkaccess credential based on location information in accordance withaspects of the subject disclosure.

FIG. 2 is a depiction of a system that facilitates sharing a networkaccess credential based on timed fingerprint location information inaccordance with aspects of the subject disclosure.

FIG. 3 illustrates a system that facilitates sharing a network accesscredential based on timed fingerprint location information in accordancewith aspects of the subject disclosure.

FIG. 4 illustrates an exemplary system including sharing a networkaccess credential based on location information in accordance withaspects of the subject disclosure.

FIG. 5 illustrates an exemplary system including sharing a networkaccess credential based on location information in accordance withaspects of the subject disclosure.

FIG. 6 illustrates a method facilitating sharing a network accesscredential based on location information in accordance with aspects ofthe subject disclosure.

FIG. 7 illustrates a method for sharing a network access credentialbased on timed fingerprint location information in accordance withaspects of the subject disclosure.

FIG. 8 illustrates a method facilitating sharing a network accesscredential based on timed fingerprint location information in accordancewith aspects of the subject disclosure.

FIG. 9 is a block diagram of an exemplary embodiment of a mobile networkplatform to implement and exploit various features or aspects of thesubject disclosure.

FIG. 10 illustrates a block diagram of a computing system operable toexecute the disclosed systems and methods in accordance with anembodiment.

DETAILED DESCRIPTION

The presently disclosed subject matter illustrates sharing a networkaccess credential based on location information. Location informationcan be determined from timed fingerprint location (TFL) information.Similarly, location information can be determined from GPS information,multilateration, triangulation, etc., though TFL information can provideadvantages over these more conventional location determinationtechnologies, as disclosed herein.

Sharing network access credentials can allow devices to access a networkbased on the shared credential. This can be advantageous over acquiringnew credentials. As an example, where a first user equipment (UE) hasnetwork access credentials for a local area network (LAN), these networkaccess credentials can be shared with a second UE to allow the second UEto access the LAN. This can eliminate, for example, the need to gothrough a registration process for new credentials for the second UE.Given that several network access credentials can be associated with thefirst UE, these credentials can be related to the location of the UE,such as a network access credential for a home LAN, a work LAN, a schoolLAN, an access point at a local coffee shop, etc. Selection of a networkaccess credential to share can be based on a location, for example, theUE can share the home LAN network access credential when the UE islocated in a region associated with the home LAN. TFL information can beemployed advantageously in determining a location as a basis forreceiving a network access credential.

TFL information can include location information or timing informationas disclosed in more detail in U.S. Ser. No. 12/712,424 filed Feb. 25,2010, which application is hereby incorporated by reference in itsentirety. Further, such information can be accessed from active state oridle state user equipment as disclosed in more detail in U.S. Ser. No.12/836,471, filed Jul. 14, 2010, which application is also herebyincorporated by reference in its entirety. As such, TFL informationcomponent can facilitate access to location information or timinginformation for a mobile device or user equipment (UE) in an active oridle state. TFL information can be information from systems in a timedfingerprint location wireless environment, such as a TFL component of awireless telecommunications carrier. As a non-limiting example, UEs,including mobile devices not equipped with a GPS-type system, can beassociated with TFL information, which can facilitate determining alocation for a UE based on the timing information associated with theUE.

In an aspect, TFL information can include information to determine adifferential value for a NodeB site pair and a bin grid frame, asdisclosed in more detail in incorporated U.S. Ser. No. 12/712,424. Acentroid region (possible locations between any site pair) for anobserved time value associated with any NodeB site pair (NBSP) can becalculated and is related to the determined value (in units of chip)from any pair of NodeBs. When UE time data is accessed, a value look-upcan be initiated (e.g., a lookup for “DV(?,X)” as disclosed in moredetail in the application incorporated herein by reference). RelevantNBSPs can be prioritized as part of the look-up. Further, the relevantpairs can be employed as an index to lookup a first primary set. As anexample, time data for a UE can be accessed in relation to a locatingevent in a TFL wireless carrier environment. In this example, it can bedetermined that a NBSP, with a first reference frame, be used forprimary set lookup with the computed DV(?,X) value as the index. Thiscan for example return a set of bin grid frame locations forming ahyperbola between the NodeBs of the NBSP. A second lookup can then beperformed for an additional relevant NBSP, with a second referenceframe, using the same value DV(?,X), as an index into the data set.Continuing the example, the returned set for the look up with secondNBSP can return a second set of bin grid frames. Thus, the UE is likelylocated in both sets of bin grid frames. Therefore, where the UE islikely in both sets, it is probable that the location for the UE is atan intersection of the two sets. Additional NBSPs can be included tofurther narrow the possible locations of the UE by providing additionalintersections among relevant bin grid sets. As such, employing TFLinformation for location determination is demonstrably different fromconventional location determination techniques or systems such as GPS,eGPS, triangulation or multilateration in wireless carrier environments,near field techniques, or proximity sensors.

Moreover, whereas TFL can be operable in a wide array of current andlegacy devices without any substantial dependence on GPS technologies, agreater number of mobile devices can act as TFL source devices thanwould be expected for GPS-enabled devices at the current time. A greaternumber of data sources are generally considered desirable infacilitating access to location information. Further, where TFLinformation can be employed in a lookup of location data sets, TFL canbe much less computationally intense than triangulation ormultilateration technologies. Reduced computational load is generallydesirable in UE devices. TFL can piggyback on timing signals employed inwireless telecommunications, which systems are already deployed. Areduced need to rollout additional hardware is generally considereddesirable. Additionally, by piggybacking on existing timing signals andby reducing the computational load, TFL can be associated with minimaladditional energy expenditure in sharp contrast to GPS ortriangulation/multilateration technologies. Reduced energy expenditureis generally related to a reduced battery drain in mobile devices and istypically a highly desirable trait.

Various embodiments relate to sharing a network access credential basedon location. In one example embodiment, a system comprises a locationcomponent that receives location information. The exemplary systemfurther comprises a credential component to determine a network accesscredential based on the location information. The network accesscredential can be distributed by way of an interface component.

In a further embodiment, a method comprises receiving locationinformation. The location information can be for a user equipment. Theexample method further comprises receiving a network access credentialbased on the location information. The network access credential canthen be accessed in the exemplary method.

In another example embodiment, a computer-readable storage mediumcomprises instructions for receiving location information for a firstuser equipment and receiving a network access credential based on thelocation information. The computer-readable storage medium furthercomprises instructions for allowing access to the network accesscredential. The access can be based on an aspect of a request foraccess. The request for access can be related to a second userequipment.

The subject disclosure is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the subject disclosure. It may be evident, however,that the subject disclosure may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to facilitate describing the subjectdisclosure.

FIG. 1 is an illustration of a system 100, which facilitates sharing anetwork access credential based on location information in accordancewith aspects of the subject disclosure. System 100 can include locationcomponent 110. Location component 110 can facilitate access to locationinformation. Location information can be received from GPS components,multilateration components, triangulation components, or any otherlocation information technology. In an embodiment, TFL information canbe a source of location information, e.g., location information derivedfrom TFL timing information, or can be a source of TFL timinginformation that can facilitate determining a location. TFL timinginformation can be for one or more NBSPs. TFL information can be derivedfrom timing associated with one or more NBSPs.

Location component 110 can be communicatively coupled with credentialscomponent 120. Credentials component 120 can select a network accesscredential based on location information. Location information can becorrelated with one or more network access credentials. Based on alocation, one or more selected network access credentials, e.g., networkaccess credentials correlated with location information, can bedetermined to be relevant. One or more of these relevant network accesscredentials can be made available to be shared with another device. Theshared network access credential can be employed to facilitate access tothe related network by the device with which the network accesscredential was shared.

In an embodiment, credentials component 120 can determine a permissionrelated to access of the one or more relevant network accesscredentials. The permission can be based on nearly any metric. As anexample, the permission can be based on information related to a networkrelated to the relevant network access credential, for instance, thenetwork can be designated as “do not share” which can lead to apermission prohibiting sharing of the relevant network accesscredential. As a second example, the network can be designated as “sharewith predetermined list A” which can lead to a permission allowingsharing of the network access credential with any device indicated on“list A”. As a third example, the permission can be based on time ofday, for instance, a permission can allow sharing in “off-peak” times.As a fourth example, the permission can be associated with particularuser inputs, for instance, a password, a user identity, a personalidentification number, a kinetic action, etc. The exemplary kineticaction, for instance, can be the act of “bumping” a first UE with asecond UE, e.g., emulating a fist-bump action between the two devices,to designate that there is an affirmative permission to share therelevant network access credential between the first and second UE.Numerous other examples are within the scope of the present subjectmatter despite not being explicitly recited for the sake of clarity andbrevity.

In an embodiment, credentials component 120 can be local with regard tolocation component 110 or interface component 130. As an example, system100 can be embodied in a cellular phone and can include credentialscomponent 120 as a component of the cellular phone. In this example, anetwork access credential correlated with location information can beselected by credentials component 120 at the cellular phone. Thiscredential can then be shared, for instance, with another cellularphone, laptop computer, tablet computer, smartphone, etc.

In another embodiment, credentials component 120 can be remote withregard to location component 110 or interface component 130. As anotherexample, credentials component 120 can be embodied in a corporate serverremote from location component 110 or interface component 130 that, forinstance, can be embodied in a tablet computer. In this example,location information, such as TFL location information, can be receivedat the tablet computer and communicated to the corporate server suchthat credentials component can determine a network access credentialbased on the location information from tablet computer. This networkaccess credential can then be shared for instance, with another cellularphone, laptop computer, tablet computer, smartphone, etc. As an example,a smartphone can enter a corporate campus having a credentials component120 embodied in a corporate server. As the smartphone enters thecorporate campus, the location information can be communicated to thecorporate server. This location information can indicate that thesmartphone is in an area served by a corporate local area network (LAN).Based on the location information indicating that the smartphone iswithin the area served by the LAN, a set of LAN access credentials canbe selected by credentials component 120. These credentials can becommunicated to the smartphone and can facilitate the smartphoneaccessing the LAN. It will be noted that the selection of thecredentials in this example is by location and not by actually detectingthe LAN itself. As such, where the smartphone has a Wi-Fi radio foraccessing the LAN, this radio can be turned off while credentials canstill be accessed based on the location, for instance, a locationdetermined by TFL information.

Credentials component 120 can be communicatively coupled with interfacecomponent 130. Interface component 130 can facilitate interaction withcredentials component 120 from other devices, for instance, a UE, laptopcomputer, tablet computer, access point, femto-cell, etc. In anembodiment, interface component 130 can include a short-rangecommunications interface to facilitate communication of a network accesscredential or request for sharing a network access credential withdevices, e.g., UEs, in a region associated with a first device, e.g., afirst UE. As an example, interface component 130 can include Bluetoothcomponents that can facilitate wirelessly sharing a network accesscredential by way of Bluetooth between a smartphone and a tabletcomputer. As a second example, interface component 130 can include802.xx components, e.g., 802.11b, 802.11g, 802.11n, ZigBee, etc., thatcan facilitate wirelessly sharing a network access credential by way ofthe 802.xx technology between two laptop computers. As a third example,interface component 130 can include 802.xx components that canfacilitate wirelessly sharing a network access credential by way of the802.xx technology between a tablet computer and an access point, e.g., aWi-Fi hotspot, corporate wireless LAN access point, etc. Short-rangecommunications can include other technologies with effective wirelessranges up to about 500 meters, though more typically on the order ofmeters to tens of meters.

FIG. 2 is a depiction of a system 200, which can facilitate sharing anetwork access credential based on timed fingerprint locationinformation in accordance with aspects of the subject disclosure. System200 can include timed fingerprint location information component (TFLIC)210. TFLIC 210 can facilitate access to location information. In anembodiment, TFL information can be location information, e.g., locationinformation derived from TFL timing information, or can be TFL timinginformation that can facilitate determining a location. TFL timinginformation can be for one or more NBSPs. TFL information can be derivedfrom timing associated with one or more NBSPs.

TFLIC 210 can be communicatively coupled with credentials component 220.Credentials component 220 can select a network access credential basedon location information. Location information can be correlated with oneor more network access credentials. Based on a location, one or moreselected network access credentials can be determined to be relevant.One or more of these relevant network access credentials can be madeavailable to be shared with another device.

Credentials component 220 can include credentials information data (CID)component 222. CID component 222 can facilitate access to credentialsinformation data. Credentials information data can include a networkaccess key, e.g., wired equivalent privacy (WEP) key, Wi-Fi protectedaccess (WPA) or Wi-Fi protected access II (WPA2) key, counter mode withcipher block chaining message authentication code protocol (CCMP) key,advanced encryption standard (AES) key, etc.; service set identifier(SSID) information; network name, network location information, e.g.,lat/long, address, range information, etc.; or other informationassociated with accessing a network. A network access credential caninclude credentials information data to facilitate access to theassociated network. As an example, a network access credential caninclude an SSID and WPA2 key that can be used by a UE to identify andaccess the network associated with the SSID.

Credentials component 220 can include network history component 224.Network history component 224 can facilitate access to historicalnetwork access information. Historical network access information caninclude data on nearly any aspect of accessing a network. As examples,historical network access information can include one or more ofhistorical dates of network access, lengths of access, data throughputfor a network access connection, quality of service or level of servicefor a network access connection, count of instances a network accessconnection has been accessed successfully/unsuccessfully/total, data onsecurity protocols for a network access connection, cost of use fornetwork access, etc. Numerous other examples of historical networkaccess information will fall within the scope of the subject disclosuredespite not being explicitly recited herein for clarity and brevity.Historical network access information can be employed in selectingrelevant network access credentials. As an example, where two networkaccess credentials are selected based on location information, a historyof poor performance for one of the networks can reduce the relevance ofthat network with regard to the other network. Credentials for this lessrelevant network can be less likely to be shared.

Credentials component 220 can include device selection component 226.Device selection component 226 can facilitate selection of appropriatedevices with which network access credentials can be shared. As anexample, device selection component 226 can indicate that only devicesthat can be identified as belonging to a designated user can be givenaccess to shared network access credentials. As a second example, deviceselection component 226 can designate that only devices with accounts ata particular telecommunications carrier can receive permission to accessshared network access credentials. As a third example, device selectioncomponent 226 can designate that access to shared network accesscredentials should conform to a list of devices, for instance a list ofphone numbers, customer numbers, account numbers, employee identifiers,device identifiers, account user names, etc.

Credentials component 220 can include permission component 228.Permission component 228 can be communicatively coupled to CID component222, network history component 224, or device selection component 226.Permission component 228 can designate a permission related to accessinga network access credential. As an example, permission component 228 candesignate that access to a network access credential is permitted basedon a requesting device being identified and affirmatively designated bydevice selection component 226 and a network access credential beingassociated with a current location of a source device. As a secondexample, permission component 228 can designate that access to a networkaccess credential is permitted based on a network access credentialbeing designated as highly relevant and being associated with a currentlocation of a source device. As a third example permission component 228can designate that access to a network access credential is denied basedon a requesting device not being identified by device selectioncomponent 226 even where a network access credential is associated witha current location of a source device. In an embodiment, permission canbe designated based on application of a set of permission rules oralgorithms to data related to a network access credential, a requestingdevice, a receiving device, network history, etc.

Credentials component 220 can be communicatively coupled to interfacecomponent 230 that can include a transmitter component 232 and areceiver component 234. Transmitter component 232 and receiver component234 can facilitate sharing a network access credential. In an embodimenttransmitter component 232 and receiver component 234 can facilitatesharing a network access credential over a wireless interface and, assuch, can include an antenna and associated electronics for wirelesscommunications. In another embodiment, transmitter component 232 andreceiver component 234 can facilitate determining aspects of an employedwireless communications technology, such as determining a typicaleffective range for sharing a network access credential over a Bluetoothlink. The determined effective range can then, for example, be employedin determining a permission related to sharing the network accesscredential.

FIG. 3 illustrates a system 300, which facilitates sharing a networkaccess credential based on timed fingerprint location information inaccordance with aspects of the subject disclosure. System 300 caninclude timed fingerprint location information component (TFLIC) 310.TFLIC 310 can facilitate access to location information. In anembodiment, TFL information can be location information, e.g., locationinformation derived from TFL timing information, or can be TFL timinginformation that can facilitate determining a location. TFL timinginformation can be for one or more NBSPs. TFL information can be derivedfrom timing associated with one or more NBSPs.

TFLIC 310 can be communicatively coupled with credentials component 320.Credentials component 320 can select a network access credential basedon location information. Location information can be correlated with oneor more network access credentials. Based on a location, one or moreselected network access credentials can be determined to be relevant.One or more of these relevant network access credentials can be madeavailable to be shared with another device. In an embodiment,credentials component 320 can be local with regard to location component310 or interface component 330. In another embodiment, credentialscomponent 320 can be remote with regard to location component 310 orinterface component 330.

Credentials component 320 can be communicatively coupled with remotecredential provisioning (RCP) component 340. In an embodiment, RCPcomponent 340 can facilitate access to credential information data.Credential information data can include information relating toaccessing a network. Credential information data can therefore includepasscodes, passwords, SSIDs, keys, device identifiers, user identifiers,service provider identifiers, network identifiers, etc. As an example,RCP component 340 can be a cloud based data store including SSIDs,locations, and WEP keys. Exemplary RCP component 340 can provide accessto this information from credentials component 320, which can be localto a device including TFLIC 310, such as a smartphone, or remote from adevice including TFLIC 310, such as a laptop computer accessing acredentials component 320 on a corporate computer system.

In an embodiment, RCP component 340 can designate a permission relatedto accessing a network access credential. A permission can be designatedbased on application of a set of permission rules or algorithms to datarelated to a network access credential, a requesting device, a receivingdevice, network history, etc. As an example, RCP component 340 canreceive an identifier and can designate a permission relating to accessof a network access credential based on the identifier. In this example,for instance, a smartphone requesting sharing of a network accesscredential can be identified by telephone number that can be compared toa list of phone numbers allowed access to a network access credential.Where the exemplary telephone number is on the list of allowedidentifiers, a permission can be set allowing the smartphone to access ashared network access credential. Where the exemplary telephone numberis not on the list of allow identifiers, a permission can be setrequiring additional verification before allowing access, denying accessentirely, allowing access to an alternate network access credential,etc. It will be noted that numerous other examples of a permission andlogic associated with determining the permission are considered withinthe scope of the disclosed subject matter despite not being explicitlyrecited for the sake of clarity and brevity.

Credentials component 320 can be communicatively coupled to interfacecomponent 330 that can include a transmitter component 332 and areceiver component 334. Transmitter component 332 and receiver component334 can facilitate sharing a network access credential. In anembodiment, transmitter component 332 and receiver component 334 can beelectronics or software for wireless communications, such as thoseenumerated elsewhere herein.

Interface component 330 can be communicatively coupled to antennacomponent 336. Antenna component 336 can facilitate communicatingbetween UEs by way of a radio access network. As an example, UEs cancommunicate over a cellular telecommunications network. Antennacomponent 336 can include medium-range antenna components, long-rangeantenna components, etc. In an embodiment, antenna component 336 doesnot include short-range antenna components that are included inshort-range antenna component 338. In some embodiments, antennacomponent 336 can be employed to facilitate communication betweencredentials component 320 and RCP component 340.

Interface component 330 can be communicatively coupled to short-rangeantenna component 338. Short-range antenna component 338 can facilitatecommunicating between UEs to facilitate sharing TFL information by wayof a short-range communication technology. The short-range communicationtechnology, for example, can be infrared, optical, Bluetooth, ZigBee,802.xx, etc. In some embodiments, short-range antenna component 338 canbe associated with predetermined transmission ranges. These transmissionranges can be, for example, associated with a personal area network thatcan include devices within about 1-3 meters of the short-range antenna;a home area network that can include devices within about 150 meters ofthe short-range antenna; a work area network that can extend out toabout 500 meters of the short-range antenna, etc. Short-rangecommunications can include technologies with effective wireless rangesup to about 500 meters, though they can more typically be on the orderof meters to tens of meters. As an example, a personal area network canbe limited to devices on or near a user and can, for example, beassociated with a range of about 1-3 meters. The exemplary short-rangeantenna component 338 covering about 1-3 meters would facilitate sharingnetwork access credentials from a source device to other devices withinabout 1-3 meters of the source device. This, for example, can be anefficient way of sharing network access credentials among devices of asingle person, such as sharing a network access credential from a cellphone to a laptop, watch, PDA, running shoe fob, etc., of a user toenable those devices to access the network for which the user alreadyhas credentials without needing to manually enter them on each device.Other ranges can be employed and are within the scope of the presentdisclosure despite not being explicitly recited.

FIG. 4 is illustrates an exemplary system 400 including sharing anetwork access credential based on location information in accordancewith aspects of the subject disclosure. System 400 can include NodeBs498A-D. Combinations of NodeBs 498A-D can act as NBSPs for determiningTFL information. UE 480 can be a TFL-enabled UE. UE 480 can acquire TFLtiming or location information relative to NodeBs 498A-D. UE 480 can beassociated with a short-range communication region 483. UE 480 can be asource device for sharing network access credentials. As an example, UE480 can have network access credentials for accessing a networkassociated with wireless access point 484.

System 400 can further include UE 482. UE 482 can be a requestingdevice. As an example, UE 482 can be without access credentials foraccessing wireless access point 484. UE 482 can generate a request forshared network access credentials. This request can be received by UE480. UE 480 can determine its location, e.g., based on TFL information.The location can be correlated with a set of relevant network accesscredentials for a network associated with access point 484. UE 480 canthen determine that the requesting device, UE 482, has permission toaccess the set of relevant access credentials. This permission can bebased, for instance, on the wireless service provider being the same forboth UE 480 and UE 482, the network associated with access point 484being open to all users, the users of UE 480 and UE 482 doing afist-bump kinetic action that indicates that a credentials transferbetween the two “bumped” device is approved by the users, etc. Theexemplary set of relevant network access credentials can then be madeaccessible form UE 480, for instance, by transmitting the credentialswithin the short-range communication region 483 with a short-rangeantenna component (not illustrated). UE 482 can receive the sharednetwork access credentials. UE 482 can then employ the credentials inaccessing the network associated with access point 484.

In an aspect, UE 486 can be outside the short-range communication region483 and can thus be unable to receive the shared network accesscredentials. In another aspect, UE 486 can be determined not to havepermission to access the shared network access credentials. Where UE 486does not have permission, but is within range (not illustrated)transmitting the credentials in an encoded manner can facilitatepreventing UE 486 from accessing the shared network access credentials.Other selective transmission techniques can also be employed, forexample, emailing the credentials to an address designated by UE 482,texting the credentials to UE 482, transmitting over a more limitedrange that includes UE 482 but exclude UE 486, etc. These, and othertechniques not explicitly recited herein for clarity and brevity, are tobe considered within the scope of the presently disclosed subjectmatter.

FIG. 5 illustrates an exemplary system 500 including sharing a networkaccess credential based on location information in accordance withaspects of the subject disclosure. System 500 can include NodeBs 598A-D.Combinations of NodeBs 598A-D can act as NBSPs for determining TFLinformation. UE 580 can be a TFL-enabled UE. UE 580 can acquire TFLtiming or location information relative to NodeBs 598A-D. UE 580 can beassociated with a short-range communication region 581. UE 580 can be aTFL source device.

UE 580 can be within region 583 associated, for example, with acorporate campus for a corporation in building 582. Access point 584 canservice region 583 with access to a wireless network. UE 580 can becommunicatively connected to RCP component 540. Further, UE 580 canrequest network access data from RCP component 540 based on the locationof UE 580 within region 583. The location of UE 580 within region 583can be determined from location data, e.g., TFL information.

In an embodiment, RCP component 540 can be embodied in a computingsystem remote from UE 580. UE 580 can be associated with a permissionfor access to a network access credential. As an example, UE 580 can bea corporate issued smartphone that can have a subscriber identity module(SIM). The SIM information can be received by RCP component 540. The SIMinformation can be compared to a list of corporate devices withpermission to access the network associate with access point 584. Wherethe SIM information matches an identified and approved device, a networkaccess credential can be shared with UE 580. Sharing the network accesscredential can be by any appropriate communications protocol, forinstance, texting, encrypted transmission, email, etc.

In some embodiments, RCP component 540 can be remote from both UE 580and building 582. RCP component 540 can be administered by a thirdparty. As examples, RCP component 540 can be a cloud based component;RCP component 540 can be a corporate computing element located in aforeign country; RCP component 540 can be a corporate computing elementadministered by a vendor company; etc.

FIGS. 4 and 5 are presented only to better illustrate some of thebenefits of the presently disclosed subject matter and are explicitlynot intended to limit the scope of the disclosure to the various aspectsparticular to the presently illustrated non-limiting example. In someembodiments, the use of GPS or other location technology can be includedinstead of, or as complimentary to, TFL information without departingfrom the scope of the present disclosure. It is noteworthy that GPS orother location information from a UE is not required to determine TFLinformation as disclosed in the related application. Thus, even wherelegacy UEs, e.g., UEs without GPS or eGPS capabilities, are representedin systems 400 and 500, the timing information from those legacy devicescan be employed in TFL information determinations. This can beparticularly useful in regions that have limited distribution of GPSenabled UEs or where GPS functions poorly due to environmental factorssuch as urban cores, mountainous regions, etc.

In view of the example system(s) described above, example method(s) thatcan be implemented in accordance with the disclosed subject matter canbe better appreciated with reference to flowcharts in FIG. 6-FIG. 8. Forpurposes of simplicity of explanation, example methods disclosed hereinare presented and described as a series of acts; however, it is to beunderstood and appreciated that the claimed subject matter is notlimited by the order of acts, as some acts may occur in different ordersand/or concurrently with other acts from that shown and describedherein. For example, one or more example methods disclosed herein couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methodologies.Furthermore, not all illustrated acts may be required to implement adescribed example method in accordance with the subject specification.Further yet, two or more of the disclosed example methods can beimplemented in combination with each other, to accomplish one or moreaspects herein described. It should be further appreciated that theexample methods disclosed throughout the subject specification arecapable of being stored on an article of manufacture (e.g., acomputer-readable medium) to allow transporting and transferring suchmethods to computers for execution, and thus implementation, by aprocessor or for storage in a memory.

FIG. 6 illustrates aspects of a method 600 facilitating sharing anetwork access credential based on location information in accordancewith aspects of the subject disclosure. At 610, TFL information can bereceived. TFL information can be location information derived from TFLtiming information or TFL timing information that can facilitatedetermining a location. TFL information can include information todetermine a differential value for a NodeB site pair and a bin gridframe, as disclosed in more detail in incorporated U.S. Ser. No.12/712,424.

TFL information can include location information or timing informationas disclosed in more detail in U.S. Ser. No. 12/712,424 filed Feb. 25,2010, which application is hereby incorporated by reference in itsentirety. Further, such information can be received from active state oridle state user equipment as disclosed in more detail in U.S. Ser. No.12/836,471, filed Jul. 14, 2010, which application is also herebyincorporated by reference in its entirety. As such, TFL information caninclude location information for a UE, in an active or idle state, basedon timing information. As a non-limiting example, a mobile device,including mobile devices not equipped with a GPS-type system, can belocated by looking up timing information associated with the mobiledevice from a TFL information reference. As such, the exemplary mobiledevice can be located using TFL information without employing GPS-typetechniques. In an aspect, TFL information can include information todetermine a DV(?,X). The centroid region (possible locations between anysite pair) for an observed time value associated with any NodeB sitepair (NBSP) can be calculated and is related to the determined value (inunits of chip) from any pair of NodeBs. When UE time data is accessed, aDV(?,X) look-up can be initiated. Relevant NBSPs can be prioritized aspart of the look-up. Further, the relevant pairs can be employed as anindex to lookup a first primary set. As an example, time data for a UEcan be accessed in relation to a locating event in a TFL wirelesscarrier environment. In this example, it can be determined that a NBSP,with a first reference frame, be used for primary set lookup with thecomputed DV(?,X) value as the index. This can for example return a setof bin grid frames locations forming a hyperbola between the NodeBs ofthe NBSP. A second lookup can then be performed for an additionalrelevant NBSP, with a second reference frame, using the same valueDV(?,X), as an index into the data set. Continuing the example, thereturned set for the look up with second NBSP can return a second set ofbin grid frames. Thus, the UE is likely located in both sets of bin gridframes. Therefore, where the UE is most likely in both sets, it isprobable that the location for the UE is at the intersection of the twosets. Additional NBSPs can be included to further narrow the possiblelocations of the UE. Employing TFL information for locationdetermination is demonstrably different from conventional locationdetermination techniques or systems such as GPS, eGPS, triangulation ormultilateration in wireless carrier environments, near field techniques,or proximity sensors.

At 620, a network access credential can be received. The network accesscredential can be correlated with location information. As such, TFLinformation can be employed to select a relevant network accesscredential. The network access credential can include credentialsinformation data to facilitate access to an associated network. As anexample, a network access credential can include a network identifierand password that can be used by a UE to identify and access the networkassociated with the network identifier. Credentials information data caninclude a network access key, e.g., WEP key, WPA or WPA2 key, CCMP key,AES key, etc.; SSID information; network name, network locationinformation, e.g., lat/long, address, range information, etc.; or otherinformation associated with accessing a network.

At 630, a permission related to accessing the network access credentialcan be determined. Access to a network can be related to a permission. Apermission can include open access, limited access, or no access.Determining a permission can be associated with a allowing a requestingentity access to a network having a predetermined access policy. Apredetermined access policy can be embodied in a set of rules or a logicapplied to determining a permission based on the entity requestingaccess and the network to be accessed. As an example, where a network isopen to any user, a permission can simply be determined to allow anyuser access to the network. As a second example, where a network accesspolicy limits access to subscribers to a service, a permission can limitaccess to a shared network access credential to subscribers to theservice, for instance by verifying a customer number, subscriberidentity, credit card number, device identifier, etc.

At 640, access to the network access credential can be allowed based onthe related permission. At this point, method 600 can end. A permissionthat limits access to the network access credential can be applied at640 to limit access to the network access credential. As an example,where a first UE requests access to a shared network access credential,a permission can be determined denying access where the UE has not paida monthly fee. As such, at 640, the first UE would not be allowed toaccess the network access credential by method 600. As a second example,where a first UE requests access to a shared network access credential,a permission can be determined granting access because the UE is ownedby Company X and the UE is located at Company X headquarters. As such,at 640, the first UE would be allowed to access the network accesscredential by method 600.

FIG. 7 illustrates aspects of a method 700 for sharing a network accesscredential based on timed fingerprint location information in accordancewith aspects of the subject disclosure. At 710, TFL information can bereceived from a first mobile device. TFL information can be locationinformation derived from TFL timing information or TFL timinginformation that can facilitate determining a location. At 720, anetwork access credential can be accessed. The network access credentialcan be correlated with location information, such as TFL informationfrom the first mobile device. This location information, e.g., TFLinformation, can be employed to select a relevant network accesscredential. The network access credential can include credentialsinformation data to facilitate access to an associated network.

At 730, a request for access to the network access credential can bereceived. The request can be from a second mobile device. At 740, inresponse to receiving the request for access to the network accesscredential, a permission can be determined. The permission can berelated to allowing access to the relevant network access credential. Inan aspect, the permission can be based on the request from the secondmobile device. Allowing access can be premised on satisfaction of anaccess policy. Wherein allowing the second mobile device to access therelevant network access credential would satisfy the access policy, apermission can be determined that can facilitate access to thecredential.

At 750, access to the network access credential can be allowed for thesecond mobile device. Allowing access can be based on the determinedpermission from 740. At this point, method 700 can end. As such, accesscan be granted where a permission has been received indicating thataccess should be granted. This permission can be based on the requestfrom the second mobile device satisfying a policy on access to thenetwork access credential. As an example, wherein the request is foraccess and the access policy for the relevant network is that thenetwork is open to any device, a permission can be determined to allowaccess to the network access credential. As a second example, where therequest is for access from a second device belonging to a user and theaccess policy for the relevant network is to allow access to the devicesof the user, a permission can be determined to allow access to thenetwork access credential. As a third example, where the requestingdevice is serviced by wireless carrier A and the access policy if toallow access to devices serviced by wireless carrier B only, apermission can be determined to deny access to the network accesscredential.

FIG. 8 illustrates a method 800 facilitating sharing a network accesscredential based on timed fingerprint location information in accordancewith aspects of the subject disclosure. At 810, location information fora mobile device can be received. The location information can bereceived at a remote credential provisioning component. A remotecredential provisioning component can facilitate access to credentialinformation data. Credential information data can include informationrelating to accessing a network. At 820, aspect information for themobile device can be received at the remote credential provisioningcomponent. Aspect information for the mobile device can includeidentification of a user, a type of mobile device, a feature of themobile device, a service provider of the mobile device, a specificationof the mobile device, or any other information relating to an aspect ofthe mobile device. This aspect information can be employed indetermining a permission when applying an access policy with regard tothe mobile device and a relevant network.

At 830, a network access credential can be access based on the locationinformation. Location information can be correlated with networks andaccess credentials for those networks. As an example, a vehicle networkcan be correlated with the position of the vehicle of the vehiclenetwork. Where a UE is collocated with the vehicle, access to thevehicle network can be desirable. As such, where an access credential tothe vehicle network is available, it can be correlated with the locationof the vehicle as well. Thus, where a first user wants to share thevehicle network access credential with other devices in the location ofthe vehicle, this can be facilitated by selecting relevant networkaccess credentials to share, e.g., selecting the vehicle networkcredentials because they are collocated with the device seeking to sharethose same credentials.

At 840, a permission can be determined. The permission can be related toaccess of the network access credentials. The permission can be based onthe aspect information received at 820. Allowing access can be premisedon satisfaction of an access policy. Wherein allowing the mobile deviceto access the relevant network access credential would satisfy theaccess policy, a permission can be determined that can facilitate accessto the credential. Satisfaction of the access policy can be based on theaspect information. As an example, the aspect information can includeinformation of the owner of the mobile device. Where the exemplarymobile device is owned by a corporation and used by a corporationemployee, this can satisfy an access policy to allow network access tocorporation owned devices. As such, a permission allowing access to thenetwork access credential can be determined that will facilitate accessto the credential based on satisfaction of the exemplary access policybased on the aspect information of the mobile device. Wherein aspectinformation can be related to almost any aspect of the mobile device, awide variety of access policies can be employed in determining apermission. All such aspect information permutations are within thepresent scope despite not being explicitly recited for clarity andbrevity.

At 850, access to the network access credential can be allowed for themobile device. Allowing access can be based on the determined permissionfrom 840. At this point, method 800 can end. As an example, where astudent registered at a university comes on campus, the student'slocation can be associated with the student being within an areaserviced by the university wireless network. The student's laptop canprovide location information, for instance, TFL information. Thisinformation can be received by remote credential provisioning componentof the university. The student's laptop can also be identified byhardware address information that can also be received at the remotecredential provisioning component of the university. A network accesscredential can be accessed based on the location of the student'slaptop, for instance, a network access credential for a North campusaccess point where the student laptop is located in the North part ofthe university campus. A permission can be determined to allow access tothe North campus credential based on a determination that being astudent laptop satisfies an access policy giving students access touniversity network resources. This permission can allow the laptop toaccess the network access credential for the North campus access pointto facilitate the laptop gaining access to the university network.

FIG. 9 presents an example embodiment 900 of a mobile network platform910 that can implement and exploit one or more aspects of the subjectmatter described herein. Generally, wireless network platform 910 caninclude components, e.g., nodes, gateways, interfaces, servers, ordisparate platforms, that facilitate both packet-switched (PS) (e.g.,internet protocol (IP), frame relay, asynchronous transfer mode (ATM))and circuit-switched (CS) traffic (e.g., voice and data), as well ascontrol generation for networked wireless telecommunication. As anon-limiting example, wireless network platform 910 can be included aspart of a telecommunications carrier network. Mobile network platform910 includes CS gateway node(s) 912 which can interface CS trafficreceived from legacy networks like telephony network(s) 940 (e.g.,public switched telephone network (PSTN), or public land mobile network(PLMN)) or a signaling system #7 (SS7) network 970. Circuit switchedgateway node(s) 912 can authorize and authenticate traffic (e.g., voice)arising from such networks. Additionally, CS gateway node(s) 912 canaccess mobility, or roaming, data generated through SS7 network 970; forinstance, mobility data stored in a visited location register (VLR),which can reside in memory 930. Further, network access credentials canbe stored in memory 930. Similarly, location information, such as TFLinformation, can be stored in memory 930. In an aspect, the TFLinformation can be based on timing signals associated with communicationbetween mobile network platform 910 and mobile device 975 by way of RAN970. Moreover, CS gateway node(s) 912 interfaces CS-based traffic andsignaling and PS gateway node(s) 918. As an example, in a 3GPP UMTSnetwork, CS gateway node(s) 912 can be realized at least in part ingateway GPRS support node(s) (GGSN). It should be appreciated thatfunctionality and specific operation of CS gateway node(s) 912, PSgateway node(s) 918, and serving node(s) 916, can be provided anddictated by radio technology(ies) utilized by mobile network platform910 for telecommunication.

In addition to receiving and processing CS-switched traffic andsignaling, PS gateway node(s) 918 can authorize and authenticatePS-based data sessions with served mobile devices. Data sessions caninclude traffic, or content(s), exchanged with networks external to thewireless network platform 910, like wide area network(s) (WANs) 950,enterprise network(s) 970, and service network(s) 980, which can beembodied in local area network(s) (LANs), can also be interfaced withmobile network platform 910 through PS gateway node(s) 918. It is to benoted that WANs 950 and enterprise network(s) 960 can embody, at leastin part, a service network(s) like IP multimedia subsystem (IMS). Basedon radio technology layer(s) available in technology resource(s) 917,packet-switched gateway node(s) 918 can generate packet data protocolcontexts when a data session is established; other data structures thatfacilitate routing of packetized data also can be generated. To thatend, in an aspect, PS gateway node(s) 918 can include a tunnel interface(e.g., tunnel termination gateway (TTG) in 3GPP UMTS network(s) (notshown)) which can facilitate packetized communication with disparatewireless network(s), such as Wi-Fi networks.

In embodiment 900, wireless network platform 910 also includes servingnode(s) 916 that, based upon available radio technology layer(s) withintechnology resource(s) 917, convey the various packetized flows of datastreams received through PS gateway node(s) 918. It is to be noted thatfor technology resource(s) 917 that rely primarily on CS communication,server node(s) can deliver traffic without reliance on PS gatewaynode(s) 918; for example, server node(s) can embody at least in part amobile switching center. As an example, in a 3GPP UMTS network, servingnode(s) 916 can be embodied in serving GPRS support node(s) (SGSN).

For radio technologies that exploit packetized communication, server(s)914 in wireless network platform 910 can execute numerous applicationsthat can generate multiple disparate packetized data streams or flows,and manage (e.g., schedule, queue, format . . . ) such flows. Suchapplication(s) can include add-on features to standard services (forexample, provisioning, billing, customer support . . . ) provided bywireless network platform 910. Data streams (e.g., content(s) that arepart of a voice call or data session) can be conveyed to PS gatewaynode(s) 918 for authorization/authentication and initiation of a datasession, and to serving node(s) 916 for communication thereafter. Inaddition to application server, server(s) 914 can include utilityserver(s), a utility server can include a provisioning server, anoperations and maintenance server, a security server that can implementat least in part a certificate authority and firewalls as well as othersecurity mechanisms, and the like. In an aspect, security server(s)secure communication served through wireless network platform 910 toensure network's operation and data integrity in addition toauthorization and authentication procedures that CS gateway node(s) 912and PS gateway node(s) 918 can enact. Moreover, provisioning server(s)can provision services from external network(s) like networks operatedby a disparate service provider; for instance, WAN 950 or GlobalPositioning System (GPS) network(s) (not shown). Provisioning server(s)can also provision coverage through networks associated to wirelessnetwork platform 910 (e.g., deployed and operated by the same serviceprovider), such as femto-cell network(s) (not shown) that enhancewireless service coverage within indoor confined spaces and offload RANresources in order to enhance subscriber service experience within ahome or business environment.

It is to be noted that server(s) 914 can include one or more processorsconfigured to confer at least in part the functionality of macro networkplatform 910. To that end, the one or more processor can execute codeinstructions stored in memory 930, for example. It should be appreciatedthat server(s) 914 can include a content manager 915, which operates insubstantially the same manner as described hereinbefore.

In example embodiment 900, memory 930 can store information related tooperation of wireless network platform 910. Other operationalinformation can include provisioning information of mobile devicesserved through wireless platform network 910, subscriber databases;application intelligence, pricing schemes, e.g., promotional rates,flat-rate programs, couponing campaigns; technical specification(s)consistent with telecommunication protocols for operation of disparateradio, or wireless, technology layers; and so forth. Memory 930 can alsostore information from at least one of telephony network(s) 940, WAN950, enterprise network(s) 960, or SS7 network 970. In an aspect, memory930 can be, for example, accessed as part of a data store component oras a remotely connected memory store.

In order to provide a context for the various aspects of the disclosedsubject matter, FIG. 10, and the following discussion, are intended toprovide a brief, general description of a suitable environment in whichthe various aspects of the disclosed subject matter can be implemented.While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatthe disclosed subject matter also can be implemented in combination withother program modules. Generally, program modules include routines,programs, components, data structures, etc. that perform particulartasks and/or implement particular abstract data types.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory.

By way of illustration, and not limitation, nonvolatile memory, forexample, can be included in volatile memory 1020, non-volatile memory1022 (see below), disk storage 1024 (see below), and memory storage 1046(see below). Further, nonvolatile memory can be included in read onlymemory (ROM), programmable ROM (PROM), electrically programmable ROM(EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatilememory can include random access memory (RAM), which acts as externalcache memory. By way of illustration and not limitation, RAM isavailable in many forms such as synchronous RAM (SRAM), dynamic RAM(DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM),enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM(DRRAM). Additionally, the disclosed memory components of systems ormethods herein are intended to comprise, without being limited tocomprising, these and any other suitable types of memory.

Moreover, it will be noted that the disclosed subject matter can bepracticed with other computer system configurations, includingsingle-processor or multiprocessor computer systems, mini-computingdevices, mainframe computers, as well as personal computers, hand-heldcomputing devices (e.g., PDA, phone, watch, tablet computers, . . . ),microprocessor-based or programmable consumer or industrial electronics,and the like. The illustrated aspects can also be practiced indistributed computing environments where tasks are performed by remoteprocessing devices that are linked through a communications network;however, some if not all aspects of the subject disclosure can bepracticed on stand-alone computers. In a distributed computingenvironment, program modules can be located in both local and remotememory storage devices.

FIG. 10 illustrates a block diagram of a computing system 1000 operableto execute the disclosed systems and methods in accordance with anembodiment. Computer 1012 includes a processing unit 1014, a systemmemory 1016, and a system bus 1018. In an embodiment, computer 1012 canbe part of the hardware of a timed fingerprint location component. In afurther embodiment, computer 1012 can be part of a remote credentialprovisioning component to facilitate access to credentials. System bus1018 couples system components including, but not limited to, systemmemory 1016 to processing unit 1014. Processing unit 1014 can be any ofvarious available processors. Dual microprocessors and othermultiprocessor architectures also can be employed as processing unit1014.

System bus 1018 can be any of several types of bus structure(s)including a memory bus or a memory controller, a peripheral bus or anexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, Industrial StandardArchitecture (ISA), Micro-Channel Architecture (MSA), Extended ISA(EISA), Intelligent Drive Electronics, VESA Local Bus (VLB), PeripheralComponent Interconnect (PCI), Card Bus, Universal Serial Bus (USB),Advanced Graphics Port (AGP), Personal Computer Memory CardInternational Association bus (PCMCIA), Firewire (IEEE 1194), and SmallComputer Systems Interface (SCSI).

System memory 1016 includes volatile memory 1020 and nonvolatile memory1022. A basic input/output system (BIOS), containing routines totransfer information between elements within computer 1012, such asduring start-up, can be stored in nonvolatile memory 1022. By way ofillustration, and not limitation, nonvolatile memory 1022 can includeROM, PROM, EPROM, EEPROM, or flash memory. Volatile memory 1020 includesRAM, which acts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as SRAM, dynamic RAM(DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM),enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), Rambus direct RAM(RDRAM), direct Rambus dynamic RAM (DRDRAM), and Rambus dynamic RAM(RDRAM).

Computer 1012 also includes removable/non-removable,volatile/non-volatile computer storage media. FIG. 10 illustrates, forexample, disk storage 1024. Disk storage 1024 includes, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, flash memory card, or memory stick. In addition, disk storage1024 can include storage media separately or in combination with otherstorage media including, but not limited to, an optical disk drive suchas a compact disk ROM device (CD-ROM), CD recordable drive (CD-R Drive),CD rewritable drive (CD-RW Drive) or a digital versatile disk ROM drive(DVD-ROM). To facilitate connection of the disk storage devices 1024 tosystem bus 1018, a removable or non-removable interface can be used,such as interface 1026. In an embodiment, disk storage 1024 can storeTFL lookup tables to facilitate lookup of location information based onNodeB site pairs and time values. In another embodiment, disk storage1024 can store TFL location information. In a further embodiment,network access credentials can be stored on disk storage 1024.Similarly, network history can be stored on disk storage 1024.

Computing devices can include a variety of media, which can includecomputer-readable storage media or communications media, which two termsare used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible and/or non-transitorymedia which can be used to store desired information. Computer-readablestorage media can be accessed by one or more local or remote computingdevices, e.g., via access requests, queries or other data retrievalprotocols, for a variety of operations with respect to the informationstored by the medium.

Communications media can embody computer-readable instructions, datastructures, program modules, or other structured or unstructured data ina data signal such as a modulated data signal, e.g., a carrier wave orother transport mechanism, and includes any information delivery ortransport media. The term “modulated data signal” or signals refers to asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in one or more signals. By way ofexample, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

It can be noted that FIG. 10 describes software that acts as anintermediary between users and computer resources described in suitableoperating environment 1000. Such software includes an operating system1028. Operating system 1028, which can be stored on disk storage 1024,acts to control and allocate resources of computer system 1012. Systemapplications 1030 take advantage of the management of resources byoperating system 1028 through program modules 1032 and program data 1034stored either in system memory 1016 or on disk storage 1024. It is to benoted that the disclosed subject matter can be implemented with variousoperating systems or combinations of operating systems.

A user can enter commands or information into computer 1012 throughinput device(s) 1036. Input devices 1036 include, but are not limitedto, a pointing device such as a mouse, trackball, stylus, touch pad,keyboard, microphone, joystick, game pad, satellite dish, scanner, TVtuner card, digital camera, digital video camera, web camera, cellphone, smartphone, tablet computer, etc. These and other input devicesconnect to processing unit 1014 through system bus 1018 by way ofinterface port(s) 1038. Interface port(s) 1038 include, for example, aserial port, a parallel port, a game port, a universal serial bus (USB),an infrared port, a Bluetooth port, an IP port, or a logical portassociated with a wireless service, etc. Output device(s) 1040 use someof the same type of ports as input device(s) 1036.

Thus, for example, a USB port can be used to provide input to computer1012 and to output information from computer 1012 to an output device1040. Output adapter 1042 is provided to illustrate that there are someoutput devices 1040 like monitors, speakers, and printers, among otheroutput devices 1040, which use special adapters. Output adapters 1042include, by way of illustration and not limitation, video and soundcards that provide means of connection between output device 1040 andsystem bus 1018. It should be noted that other devices and/or systems ofdevices provide both input and output capabilities such as remotecomputer(s) 1044.

Computer 1012 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1044. Remote computer(s) 1044 can be a personal computer, a server, arouter, a network PC, a workstation, a microprocessor based appliance, apeer device, or other common network node and the like, and can includemany or all of the elements described relative to computer 1012.

For purposes of brevity, only a memory storage device 1046 isillustrated with remote computer(s) 1044. Remote computer(s) 1044 can belogically connected to computer 1012 through a network interface 1048and then physically connected by way of communication connection 1050.Network interface 1048 encompasses wire and/or wireless communicationnetworks such as local-area networks (LAN) and wide-area networks (WAN).LAN technologies include Fiber Distributed Data Interface (FDDI), CopperDistributed Data Interface (CDDI), Ethernet, Token Ring and the like.WAN technologies include, but are not limited to, point-to-point links,circuit switching networks like Integrated Services Digital Networks(ISDN) and variations thereon, packet switching networks, and DigitalSubscriber Lines (DSL). As noted below, wireless technologies may beused in addition to or in place of the foregoing.

Communication connection(s) 1050 refer(s) to hardware/software employedto connect network interface 1048 to bus 1018. While communicationconnection 1050 is shown for illustrative clarity inside computer 1012,it can also be external to computer 1012. The hardware/software forconnection to network interface 1048 can include, for example, internaland external technologies such as modems, including regular telephonegrade modems, cable modems and DSL modems, ISDN adapters, and Ethernetcards.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches, and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which can be operated by a software or firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can include a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Moreover, terms like “user equipment (UE),” “mobile station,” “mobile,”subscriber station,” “subscriber equipment,” “access terminal,”“terminal,” “handset,” and similar terminology, refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Likewise, the terms “access point (AP),” “basestation,” “Node B,” “evolved Node B (eNode B),” “home Node B (HNB),”“home access point (HAP),” and the like, are utilized interchangeably inthe subject application, and refer to a wireless network component orappliance that serves and receives data, control, voice, video, sound,gaming, or substantially any data-stream or signaling-stream to and froma set of subscriber stations or provider enabled devices. Data andsignaling streams can include packetized or frame-based flows.

Additionally, the term “core-network”, “core”, “core carrier network”,or similar terms can refer to components of a telecommunications networkthat provide some or all of aggregation, authentication, call controland switching, charging, service invocation, or gateways. Aggregationcan refer to the highest level of aggregation in a service providernetwork wherein the next level in the hierarchy under the core nodes canbe the distribution networks and then the edge networks. UEs do notnormally connect directly to the core networks of a large serviceprovider but can be routed to the core by way of a switch or radio areanetwork. Authentication can refer to determinations regarding whetherthe user requesting a service from the telecom network is authorized todo so within this network or not. Call control and switching can referdeterminations related to the future course of a call stream acrosscarrier equipment based on the call signal processing. Charging can berelated to the collation and processing of charging data generated byvarious network nodes. Two common types of charging mechanisms found inpresent day networks can be prepaid charging and postpaid charging.Service invocation can occur based on some explicit action (e.g. calltransfer) or implicitly (e.g., call waiting). It is to be noted thatservice “execution” may or may not be a core network functionality asthird party network/nodes may take part in actual service execution. Agateway can be present in the core network to access other networks.Gateway functionality can be dependent on the type of the interface withanother network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components (e.g., supportedthrough artificial intelligence, as through a capacity to makeinferences based on complex mathematical formalisms), that can providesimulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploitedin substantially any, or any, wired, broadcast, wirelesstelecommunication, radio technology or network, or combinations thereof.Non-limiting examples of such technologies or networks include Geocasttechnology; broadcast technologies (e.g., sub-Hz, ELF, VLF, LF, MF, HF,VHF, UHF, SHF, THz broadcasts, etc.); Ethernet; X.25; powerline-typenetworking (e.g., PowerLine AV Ethernet, etc.); femto-cell technology;Wi-Fi; Zigbee, other 802.XX wireless technologies, WorldwideInteroperability for Microwave Access (WiMAX); Enhanced General PacketRadio Service (Enhanced GPRS); Third Generation Partnership Project(3GPP or 3G) Long Term Evolution (LTE); 3GPP Universal MobileTelecommunications System (UMTS) or 3GPP UMTS; Third GenerationPartnership Project 2 (3GPP2) Ultra Mobile Broadband (UMB); High SpeedPacket Access (HSPA); High Speed Downlink Packet Access (HSDPA); HighSpeed Uplink Packet Access (HSUPA); GSM Enhanced Data Rates for GSMEvolution (EDGE) Radio Access Network (RAN) or GERAN; UMTS TerrestrialRadio Access Network (UTRAN); or LTE Advanced.

What has been described above includes examples of systems and methodsillustrative of the disclosed subject matter. It is, of course, notpossible to describe every combination of components or methodologieshere. One of ordinary skill in the art may recognize that many furthercombinations and permutations of the claimed subject matter arepossible. Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

What is claimed is:
 1. A method, comprising: wirelessly sharing, by afirst user equipment comprising a processor, via a short-rangecommunications interface, a network access credential for a wirelesslocal area network with a second user equipment, to allow the seconduser equipment to access a network device of the wireless local areanetwork, wherein the wirelessly sharing comprises: receiving, by thefirst user equipment, via the short-range communications interface, anetwork access credential request from the second user equipment,selecting, by the first user equipment, the network access credentialbased on a location of the second user equipment; determining, by thefirst user equipment, permission of the second user equipment to accessthe wireless local area network, based at least in part on a useridentity associated with the second user equipment, and communicating,by the first user equipment, via the short-range communicationsinterface, the network access credential to the second user equipment.2. The method of claim 1, wherein the determining the permissioncomprises determining whether the second user equipment is a member of agroup of devices indicated have permission to access the network deviceof the wireless local area network.
 3. The method of claim 1, whereinthe determining the permission comprises determining whether the seconduser equipment is a member of a group of devices indicated to beprohibited to access the network device of the wireless local areanetwork.
 4. The method of claim 1, wherein the determining thepermission comprises accessing historical network access informationrelated to previous access to the network device of the wireless localarea network.
 5. The method of claim 1, wherein the determining thepermission comprises identifying the second user equipment as a deviceassociated with the user identity.
 6. The method of claim 1, wherein thefirst user equipment comprises a cellular telephone.
 7. The method ofclaim 1, wherein the short-range communications interface communicatesaccording to a Bluetooth wireless protocol.
 8. The method of claim 1,wherein the short-range communications interface communicates accordingto a Wi-Fi protocol.
 9. The method of claim 1, wherein the networkaccess credential comprises a Wi-Fi key.
 10. The method of claim 1,wherein the network access credential comprises a wired equivalentprivacy key, a Wi-Fi protected access key, or a Wi-Fi protected accessII key.
 11. The method of claim 1, wherein the network access credentialcomprises a service set identifier and a Wi-Fi protected access II keythat are able to be used by the second user equipment to identify andaccess the network device of the wireless local area network.
 12. Themethod of claim 1, wherein the wirelessly sharing further comprisesdetermining that the second user equipment is within a defined effectiverange to share the network access credential over a Bluetooth link. 13.A first user equipment, comprising: a processor; and a memory thatstores executable instructions that, when executed by the processor,facilitate performance of operations, comprising: determining whether asecond user equipment has a permission to access a wireless access pointdevice in a region associated with the first user equipment, based atleast in part on a user identity associated with the second userequipment; and in response to the determining indicating that the seconduser equipment has the permission to access the wireless access pointdevice, selecting a network access credential based on a location of thesecond user equipment and facilitating wirelessly sharing, via ashort-range communications interface, the network access credential withthe second user equipment.
 14. The first user equipment of claim 13,wherein the determining whether the second user equipment has thepermission comprises determining whether the second user equipment is ina predetermined list of devices indicated have the permission to accessthe wireless access point device.
 15. The first user equipment of claim13, wherein the determining whether the second user equipment has thepermission comprises determining whether the user identity is associatedwith the second user equipment as an owner of the second user equipment.16. The first user equipment of claim 13, wherein the determiningwhether the second user equipment has the permission to access thewireless access point device comprises accessing historical networkaccess information.
 17. The first user equipment of claim 13, whereinthe first user equipment comprises a cellular telephone.
 18. The firstuser equipment of claim 13, wherein the short-range communicationsinterface implements a wireless protocol from a group of wirelessprotocols, the group of wireless protocols comprising a Bluetoothprotocol and a Wi-Fi protocol.
 19. A non-transitory machine-readablemedium, comprising executable instructions that, when executed by aprocessor of a first user equipment, facilitate performance ofoperations, comprising: receiving, via a short-range communicationsinterface from a second user equipment, request data representative of anetwork access credential request applicable to network devices of awireless local area network, to enable the second user equipment toaccess a network device of the network devices of the wireless localarea network; selecting a network access credential based on a locationof the second user equipment; determining that the second user equipmentis permitted to access the network device, based at least in part on auser identity determined to be associated with the second userequipment, and communicating, by the first user equipment, via theshort-range communications interface, the network access credential tothe second user equipment; and in response to the determining, sendingthe network access credential to the second user equipment via theshort-range communications interface.
 20. The non-transitorymachine-readable medium of claim 19, wherein the network accesscredential comprises a Wi-Fi key to enable the second user equipment toaccess the network device.